Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix memory leak #224

Merged
merged 2 commits into from
Jul 31, 2023
Merged

Fix memory leak #224

merged 2 commits into from
Jul 31, 2023

Conversation

Akxe
Copy link
Contributor

@Akxe Akxe commented May 22, 2023

No description provided.

@codehippie1
Copy link
Contributor

codehippie1 commented May 25, 2023 via email

@Akxe
Copy link
Contributor Author

Akxe commented Jul 31, 2023

Just rebased. This fixes the createObjectURL memory leak using revokeObjectURL.

MDN Example

@codehippie1
Copy link
Contributor

@Akxe, You are super quick. Appreciate it. Merging

@codehippie1 codehippie1 merged commit 45f2a87 into intbot:master Jul 31, 2023
@Akxe Akxe deleted the fix-memory-leak branch July 31, 2023 14:18
@provegard
Copy link

Looks like there is still a leak when the component is destroyed, right?

@Akxe
Copy link
Contributor Author

Akxe commented Aug 8, 2023

This PR fixed one. Did you find any other?

@provegard
Copy link

I just noticed that the added relaseUrl function is not called in ngOnDestroy (which doesn't exist), so when the component is destroyed, the last object URL isn't revoked.

@Akxe
Copy link
Contributor Author

Akxe commented Aug 8, 2023

Well... It must have gotten removed when rebasing the PR on the new master...

I am out of the office. Would you create the mentioned fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants